System, methods and computer products for determining affinity to a content creator

ABSTRACT

Affinity scores are computed for a plurality of user accounts, each affinity score quantifies an affinity of a user account to a content creator of one or more digital objects hosted in a content hosting platform. Each affinity score is computed by collecting interaction data for the user account corresponding to the content creator, normalizing the collected interaction data using a total activity data of the user account on the content hosting platform and attribute data associated with the content creator, and generating the affinity score using the normalized interaction data.

BACKGROUND OF THE INVENTION I. Field

This disclosure relates generally to digital content distributionplatforms, and more particularly to systems, methods, and computerproducts for quantifying an affinity of a user account on a digitalcontent distribution platform to a content creator hosting content onthe digital content distribution platform.

II. Related Art

Digital content distribution platforms have allowed consumersunprecedented access to large catalogs of digital items (i.e. digitalobjects) such as digital media in the form of movies, TV shows andsongs, documents such as e-books and scholarly articles, and interactivecontent such as video games and mobile applications.

Users typically access these platforms (e.g. music or video streamingservices) using a personal user account and are given a number of waysin which to interact with content from a catalog, including, forexample, the ability to purchase or stream digital items, to add acontent creator (e.g. a musical artist, publisher, movie producer orauthor) to a list of favorite content creators, to follow or subscribeto a mailing list of a content creator, to add digital items to aplaylist, to download a digital item for offline access, or to share adigital item with other users on the platform or on external platformssuch as Internet-based social networks and personal blogs.

Data from these interactions can be collected over time and can be usedto provide additional features to the user such as contentrecommendation. For example, a profile can be built from interactiondata and maintained for each user account, providing insights into thepreferences of each user for certain types of digital items or certaintypes of content creators. The profile can then be used to recommenddigital items to the user. In addition, interaction data provides eachuser with a valuable historical record of their activity on the platformand of their most commonly accessed content (e.g. top played songs, topplayed artists, favorite television shows, etc.).

BRIEF DESCRIPTION

From the perspective of a content creator, being able to use interactiondata to identify particular user accounts that have a meaningfulaffinity for the digital content hosted by the content creator couldprove immensely valuable. By identifying the most meaningful “fans” orenthusiasts of their content among the many users of a platform, contentcreators could, for example, more effectively deliver targetedadvertisements to user accounts or more purposefully connect with theirmost valuable users.

However, interaction data alone can provide only limited insight intowhether a user account has any meaningful affinity to a content creator.In fact, the enormous volume of interaction data collected and thevastness of a typical content catalog add an immense level of complexityto this issue.

For example, a simple comparison of the number of times two useraccounts accessed a digital item does not take into account any of thecontextual factors required in order to compare the two user accountsfor the actual or meaningful affinity each has for the digital item.These factors may include, for example, a comparison of the totalactivity of each user on the platform, a comparison of the activity ofeach user outside of the platform, the overall popularity of the digitalitem, the overall popularity of the content creator of the digital item,or the different values associated with different types of interactions(e.g. one user sharing an item on a social media website might be moremeaningful than the other user simply downloading the item).

Although the wealth of interaction data collected on these platforms hascreated unique new opportunities for content creators to understand useraffinity or so-called “fandom”, there has yet to be a technical solutionfor quantifying affinity to a content creator using this interactiondata using hardware, software or a combination of both.

The example embodiments described herein address the foregoingdifficulties by providing methods, systems and computer program productsfor computing affinity scores for a plurality of user accounts, eachaffinity score quantifying affinity of a user account to one of aplurality of content creators hosting one or more digital objects in acontent hosting platform. Computing an affinity score includescollecting interaction data for the user account corresponding to thecontent creator, normalizing the collected interaction data using thetotal activity data of the user account on the content hosting platform,and generating the affinity score using the normalized interaction dataand attribute data associated with the content creator.

In one example embodiment, when normalizing the collected interactiondata, the interaction data can also be normalizing using activity dataof one or more other user accounts.

In another example embodiment, a ranking of the affinity score againstaffinity scores of other user accounts corresponding to the contentcreator can be generated. The user account can then be categorized intoone or more groups using the affinity score or the ranking generated forthe affinity score. For example, one of the one or more groups caninclude only user accounts having affinity scores that increased atleast a threshold amount over a time period.

In another example embodiment, the affinity score can be periodicallyupdated using a most recent activity data of the user accountcorresponding to the content creator.

In yet another embodiment, at least a portion of the total activity datafor the user account can be collected from at least one data sourceexternal to the content hosting platform.

BRIEF DESCRIPTION OF THE DRAWINGS

The features and advantages of the example embodiments of the inventionpresented herein will become more apparent from the detailed descriptionset forth below when taken in conjunction with the following drawings.

FIG. 1 is an overview of a system for determining affinity of a useraccount to a content creator according to an example embodiment of theinvention.

FIG. 2 is a sequence diagram illustrating a process for determiningaffinity of a user account to a content creator according to an exampleembodiment of the invention.

FIG. 3 is a block diagram illustrating a device configured to compute anaffinity score for a user account according to an example embodiment ofthe invention.

FIG. 4 illustrates a flow diagram of a process for computing an affinityscore for a user account according to an example embodiment of theinvention.

FIG. 5 is a block diagram of an example client-server data systemconfigured in accordance with the principles of the invention.

FIG. 6 is a block diagram of a general and/or special purpose computer,which may be a general and/or special purpose computing device, inaccordance with some of the example embodiments of the invention.

Identical reference numerals used in different figures identify the sameelements, and thus a detailed description of those elements may not beprovided herein for each separate figure.

DETAILED DESCRIPTION

The example embodiments described herein provide systems, methods andcomputer products for determining affinity to a content creator, whichare now described herein in terms of an example method for computing anaffinity score quantifying affinity of a user account to a contentcreator for use with a content distribution platform. This descriptionis not intended to limit the application to the example embodimentspresented herein. In fact, after reading the following description, itwill be apparent to one skilled in the relevant art(s) how to implementthe following example embodiments in alternative embodiments (e.g., indomains outside of music or video distribution platforms).

FIG. 1 is an overview of a system 100 for determining affinity of a useraccount to a content creator according to an example embodiment of theinvention.

Content distribution platform 110 is a platform for distributing digitalcontent to an end-user on client device 120 by delivering digitalcontent or digital objects, including, but not limited to, web objects(e.g. text, graphics and scripts), downloadable objects (e.g. mediafiles, software, documents), applications (e.g. e-commerce, portals),live streaming media, on-demand streaming media, and social mediacontent to client device 120 communicatively coupled to contentdistribution platform 110 (e.g., via a network; not shown).

Content distribution platform 110 may include a large distributed systemof servers deployed in multiple data centers across the Internet (i.e. acontent distribution network). It may, for example, include aninterconnected system of cache servers that use geographical proximityas a criterion for delivering digital content with optimized performanceand availability. Alternatively, content distribution platform 110 mayuse any other known or future known technologies for hosting anddistributing digital content to a remote client device, such aspeer-to-peer file-sharing technologies.

Content distribution platform 110 serves digital objects from a catalogof content, such as a music or video library. The catalog may includedigital objects generated by a variety of content providers such asmedia companies, artists, publishers or e-commerce vendors. Thesecontent providers may include the operator of the content distributionplatform itself or third-party content creators.

Client device 120 is computer hardware or software that accessesservices and digital objects made available by content distributionplatform 110. The client device 120 is communicatively coupled to thecontent distribution platform 110 by a network, such as through aconnection using cable, fiber optic, satellite or wireless communicationmechanisms or other known or future known communication mechanisms.

Client device 120 may also have means to display, execute or presentdigital objects to an end-user, such as a display device or audiodevice.

Client device 120 can include general purpose computer hardware in theform of a desktop computer, mobile device or set-top box. Alternatively,client device 120 can include a stand-alone device for contentconsumption such as a portable media player, radio, television orcomputer monitor. Client device 120 may also be in the form of softwareinstalled locally on a computer or accessed through the Internet, suchas a web-based application (e.g. desktop or web-based media streamingsoftware).

Client device 120 is configured to allow the end-user a number ofdifferent interactions with digital objects. For example, client device120 may include e-commerce and payment features that allow a user topurchase a digital object. Client device 120 may also allow for socialinteractions with data objects or content creators such as the abilityfor the user to add a digital object or a profile of a content creatorto a list of favorite items, to share a digital item with other users ofthe content distribution platform 110 or to share a digital item withusers on external platforms such as social media websites and personalblogs, or to add digital objects to a personalized playlist.

Client device 120 is also configured to manage one or more user accountsthrough a user account system of content distribution platform 110. Eachuser account is identified by a username. In one example embodiment, auser account system allows an end-user to authenticate to client device120 and to be granted authorization to access the services and contentsprovided by content distribution platform 110. Client device 120 canallow multiple end-users to authenticate to client device 120 each withtheir own user account. Each user account is associated with acorresponding home directory or partition of memory on the client devicewhich is used to store files pertaining exclusively to the activities ofthat end-user. This directory or partition can be protected from accessby other users. Each user account may contain a user profile, whichincludes information about the end-user, end-user selected settings, ordata collected from interactions performed by the end-user.

Once an end-user has been authenticated to or by client device 120 usinga user account, interaction data are collected including activitiesperformed by an end-user using the user account on content distributionplatform 110. These interaction data are stored in interaction datastorage 132. Interaction data storage 132 can be communicatively coupledto content distribution platform 110. Interaction data storage 132 canbe a single server or a distributed file system such as, for example,any known or future known distributed file system and associatedsoftware framework such as the Apache Hadoop Distributed File System(HDFS) and the Apache MapReduce framework.

In addition to interaction data storage 132, the system 100 of FIG. 1includes a number of other data sources including, but not limited to,social data storage 134 and attribute data storage 136.

Social data storage 134 stores social media data associated with anend-user such as activity data from one or more Internet-based socialnetworks (e.g. Facebook, Twitter, etc.). Content distribution platform110 allows an end-user to authenticate to and link their user account oncontent distribution platform 110 to a user profile from anInternet-based social network. The data may include information on anyknown or future known social interactions enabled by a social networksuch as sharing of user-generated content, “favoriting” or “liking” adigital object, or messaging other user profiles on an Internet-basedsocial network.

Attribute data storage 136 stores data describing attributes of one ormore content providers. This can include, but is not limited to,cultural data on content providers, editorial content, or popularitydata on content providers.

Affinity scoring agent 140 is configured to collect data from datasources including, for example, interaction data storage 132, socialdata storage 134 and attribute data storage 136 and to generate anaffinity score that quantifies the affinity of a particular user accountto one of the content providers serving content on content distributionplatform 110. The process by which affinity scoring agent 140 generatesan affinity score is described more fully below in view of FIGS. 3 and4.

Affinity scoring agent 140 stores the generated affinity scores inuser-affinity data storage 150, which in turn is accessible by aplurality of external systems including, but not limited to, dashboardsystem 162, messaging system 164, and event system 164.

Dashboard system 162 is a management system for content providers andallows a content provider to view an overview of the content hosted theyare hosting on content distribution platform 110 and the activity dataof user accounts that have interacted with the content hosted by thecontent provider on content distribution platform 110. In exampleembodiments described herein, dashboard system 162 can access affinityscores stored in affinity data storage 162.

The dashboard system 162 is configured to both display the affinity dataand to allow a content provider to manipulate the affinity data. It canalso be configured to allow the content provider to interact withcontent distribution platform 110 in a number of ways, such as byserving targeted advertisements to user accounts or modifying hosteddigital objects in response to the displayed or manipulated affinitydata.

Messaging system 164 is a system for content providers to communicateinformation to end-users, for example, by transmitting messages to useraccounts of content distribution platform 110. In one exampleembodiment, messaging system 164 allows for both targeted and mass-mailmessaging. In example embodiments described herein, the messaging systemcan access affinity scores stored in affinity data storage 150. Themessaging system 164 can display the affinity data and allows a contentprovider to manipulate the affinity data. In one embodiment, messagingsystem 164 allows the content provider to message user accounts ofcontent distribution platform 110 by, for example, messaging a singleuser account in response to the displayed or manipulated affinity data.

Event system 166 is a system for content providers to promote events touser accounts of the content distribution platform 110. For example,event system 166 may include a concert management system (not shown)that allows a music producing content provider to list or promoteconcert events to end-users. The event system 166 allows a contentprovider to provide, for example, date, time and location data forevents to end-users, for example, by transmitting messages to useraccounts of content distribution platform 110.

Advertisement (“ad”) server 170 is a system for content providers todisplay or present advertisements on client device 120. Ad server 170includes a computer server, such as a web server backed by a databaseserver, that stores advertising content used in marketing contentproviders and their content, and delivers advertisements to end-users ofcontent distribution platform 110. The advertising content stored on adserver 170 is constantly updated so that new advertisements aredisplayed or presented to end-users when they engage with contentdistribution platform 110. The advertisements can, for example, be inthe form of a display ad displayed on a display device of client device120 or in the form of an audio ad presented through an audio device ofclient device 120.

FIG. 2 is a sequence diagram illustrating a process for determiningaffinity of a user account to a content creator according to an exampleembodiment of the invention. The process can be performed, for example,by the system of FIG. 1.

In step S200, activity data including interactions performed by anend-user using a user account on client device 120 are logged and storedin interaction data storage 132.

In step S205, data from interaction data storage 132 as well as variousother data sources such as, for example, social data storage 134 andattribute storage 136 are sent to affinity score agent 140.

In instances where the data sources include distributed or clusteredfile systems, a batch processing of this data is performed by affinityscore agent 140 in step S210 using any known or future known programmingmodel for processing and generating large data sets using a parallel,distributed algorithm on a computer cluster, such as the ApacheMapReduce framework. Any known library for the programming model can beused, for example, the Apache Crunch framework for writing, testing andrunning MapReduce pipelines.

Affinity score agent 140 generates an affinity score that quantifies theaffinity of a particular user account to one of the content providersserving content on content distribution platform 110 using the batchedprocessed data. Affinity score agent 140 may also compute a ranking ofan affinity score or a categorization of an affinity score. Theprocesses by which affinity score agent 140 generates an affinity score,ranks an affinity score and categorizes an affinity score are describedmore fully below in view of FIGS. 3 and 4.

In step S215, the affinity score, ranking and/or categorizations (i.e.affinity data) generated by affinity score agent 140 are stored inuser-affinity database 150.

In step S220, the affinity data stored in user-affinity database 150 areaccessed by external systems including, but not limited to, dashboardsystem 162, messaging system 164, and event system 166.

In step S225, the external systems (162, 164, and 166) enable a contentprovider (not shown) to access, display, manipulate or otherwise actupon the affinity data received from user-affinity database 150.

In step S230, the external systems (162, 164, and 166) enable a contentprovider to send targeted data to client device 120 in response to theaffinity data or manipulations of the affinity data. These targeted datacan include, but are not limited to, targeted messages to a user accountor the “following” or “favoriting” of a user account (e.g. the labelingor listing of a user account as a “follower”, “favorite” or “fan” of acontent provider). Alternatively, in step S230, the external systems(162, 164, and 166) enable a content provider to send data to anexternal server in response to the affinity data or manipulations of theaffinity data, such as to ad server 170.

In step S235, an advertising line item is generated by ad server 170 inresponse to the affinity data received from one or more of the pluralityof external systems, for example, event system 164. In one embodiment,ad server 170 generates the advertising line item locally in response tothe affinity data and user account data from client device 120.Alternatively, ad server 170 may be configured to generate a templateline item to send to client device 120. The template line item mayinclude instructions for the client device to fill the template lineitem in response to affinity data accessed by client device 120 directlyfrom user-affinity database 150 and/or user account data stored onclient device 120.

In step S240, ad server 170 delivers the advertising line item to a useraccount on client device 120.

FIG. 3 is a block diagram for explaining affinity scoring agent 140,illustrated in FIG. 3 as a device configured to compute an affinityscore for a user account.

As shown in FIG. 3, affinity scoring agent 140 includes computing unit300 configured to compute affinity scores for a plurality of useraccounts. Each affinity score quantifies the affinity of a user accountto one of a plurality of content creators of one or more digital objectshosted in the content hosting platform.

Computing unit 300 includes collection unit 305, which is configured tocollect user account data corresponding to one or more content creatorsfrom a variety of data sources, including, but not limited to,interaction data storage 132, social data storage 134 or attribute datastorage 136. These data sources can include data sources external to thecontent hosting platform 110.

Also included in computing unit 300 is normalization unit 310 configuredto normalize the collected user account data corresponding to aparticular content creator using the total activity data for the useraccount and attribute data of the content creator. Normalization unit310 can also be configured to normalize the collected user account datausing activity data of one or more other user accounts.

Computing unit 300 further includes score generating unit 315 configuredto generate an affinity score using the normalized user account data andstoring unit 330 configured to store the generated affinity score inuser-affinity database 150. The process steps of normalizing thecollected user account data and generating the affinity score areexplained more fully below, in view of FIG. 4.

In the example embodiment of FIG. 3, computing unit 300 also includesranking unit 320 configured to rank the generated affinity score againstaffinity scores of one or more other user accounts corresponding to thecontent creator and categorization unit 325 configured to categorize theuser account into one or more groups using the affinity score or theranking of the affinity score produced by the ranking unit.

Storing unit 330 may be further configured to store the ranking andcategorizations of the affinity score in user-affinity database 150.

Computing unit 300 and each of the components included therein may befurther configured to update the affinity score periodically using themost recent activity data of a user account corresponding to the contentcreator.

FIG. 4 illustrates a flow diagram of a process for computing an affinityscore for a user account according to an example embodiment of theinvention. The process can be performed, for example, by a speciallyconfigured device such as affinity scoring agent 140.

Briefly, in FIG. 4, an affinity score is computed for a user account,where the affinity score quantifies an affinity of the user account to acontent creator of one or more digital objects hosted in a contenthosting platform. The affinity score is computed by collectinginteraction data for the user account corresponding to the contentcreator, normalizing the collected interaction data using a totalactivity data of the user account on the content hosting platform andattribute data associated with the content creator, and generating theaffinity score using the normalized interaction data.

In step S400, data are collected from interaction data storage 132 aswell as various other data sources, for example social data storage 134and attribute storage 136 and are sent to affinity score agent 140.

A batch processing of this data is performed by affinity score agent 140in step S400 using any known or future known programming model forprocessing and generating large data sets using a parallel, distributedalgorithm on a computer cluster, such as the Apache MapReduce framework.For example, a batched processing of the data may be performed on aperiodic basis (e.g. daily, weekly or monthly). Any known library forthe programming model can be used, for example, the Apache Crunchframework for writing, testing and running MapReduce pipelines.

In step S401, one or more values indicating an affinity of the useraccount for a content provider are normalized. These values can includeany type of value that may signal an affinity or preference for adigital object hosted by the content provider; for example: data on thenumber of times a user account streamed or downloaded a digital objector the number of times a user account shared a link to a digital object.

The values are normalized using any known statistical normalizationtechniques using data collected from one or more of the plurality ofdata sources (e.g. interaction data storage 132, social data storage134, or attribute storage 136).

These normalization techniques can include any known or future knowntechniques of performing weighted adjustments of the values that allowfor the comparison of corresponding normalized values for different datasources. Example normalizations may include, but are not limited to,performing a weighted adjustment of interaction data from interactiondata storage 132 in accordance with the type of interaction performed;for example: weighting the significance given to streaming a digitalobject differently, compared to adding the digital object to a playlist.

As another example, interaction data for a single user accountcorresponding to a single content provider could be adjusted using thetotal interaction data collected for the user account across all contentproviders.

Collected data may also be normalized using data from external oralternative data sources. For example, interaction data collected frominteraction data storage 132 may be normalized using data collected fromsocial data storage 134 or attribute data storage 136.

In step S402, an affinity score is generated using the normalized data.The affinity score can be any single value that serves to quantify anaffinity of an individual user account to a single content provider.This score can then be compared between user accounts for a singlecontent provider or between content providers for a single user account.

In step S403, the generated affinity score may optionally be rankedagainst affinity scores of one or more other user accounts correspondingto the content creator. This ranking step may result in a numericalranking of the affinity score which can be stored, for example, inuser-affinity database 150.

In step S404, the user account may be categorized into one or moregroups according to the generated affinity score and/or the rankinggenerated for the affinity score. This categorization step may result inthe generation of data in the form of one or more category labels foreach affinity score which can also be stored, for example, inuser-affinity database 150. As one example, a category label can begenerated for an affinity score that has increased at least a thresholdamount over a time period. In the example of a music streaming service,this category label might label the user account as an “emerging fan” or“new fan”. Alternative category labels might label a user account as a“hardcore fan”, a “lapsed fan”, etc., when desired and/or meaningfulqualifications of an affinity of a user account for a content providerare identified using the affinity score or a change of an affinity scoreover a time period.

In step S405, the generated affinity score, ranking and orcategorization is stored in user-affinity database 150, which in turn isaccessible by a plurality of external systems including, but not limitedto, dashboard system 162, messaging system 164, and event system 164.

Steps S400 through S405 can be repeated periodically to generate anupdated affinity score.

FIG. 5 is a block diagram of an example client-server data system 500configured in accordance with the principles of the invention. Datasystem 500 can include server 502 and client device 504. In someembodiments, data system 500 can include multiple servers 502, multipleclient devices 504, or both multiple servers 502 and multiple clientdevices 504. For simplicity, only one server 502 and one client device504 are illustrated.

Server 502 may include any suitable types of servers that can store andprovide data to client device 504 (e.g., file server, database server,web server, or media server). Server 502 can store media objects andother data (e.g., metadata associated with the content of the mediaobjects), and server 502 can receive data download requests from clientdevice 504. For example, server 502 can receive requests to obtain themedia objects, such as one or more audio or video tracks or previews orloops of those audio or video tracks such as those described above.Responsive thereto, server 502 can locate and provide the requestedsongs, previews or loops as well as associated metadata, such asattributes related to the media object (e.g., genre, artist, albumtitle, album cover art, release date, and the like), mediarecommendations, and the like.

In some embodiments, server 502 can obtain and process data from one ormore client devices 504. For example server 502 can receive from claimdevice 504 requests for specific previews or loops.

Server 502 can communicate with client device 504 over communicationslink 503. Communications link 503 can include any suitable wired orwireless communications link, or combinations thereof, by which data maybe exchanged between server 502 and client 504. For example,communications link 503 can include a satellite link, a fiber-opticlink, a cable link, an Internet link, or any other suitable wired orwireless link. Communications link 503 may enable data transmissionusing any suitable communications protocol supported by the medium ofcommunications link 503. Such communications protocols may include, forexample, Wi-Fi (e.g., a 802.11 protocol), Ethernet, Bluetooth™, radiofrequency systems (e.g., 900 MHz, 2.4 GHz, and 5.6 GHz communicationsystems), infrared, TCP/IP (e.g., and the protocols used in each of theTCP/IP layers), HTTP, Bit Torrent, FTP, RTP, RTSP, SSH, any othercommunications protocol, or any combination thereof.

Client device 504 can include any electronic device capable of playingaudio or video (e.g., music, videos, podcasts, and interviews) to a userand may be operative to communicate with server 502. For example, clientdevice 504 can include a portable media player, a cellular telephone,pocket-sized personal computers, a desktop computer, a laptop computer,and any other device capable of communicating via wires or wirelessly(with or without the aid of a wireless enabling accessory device).

FIG. 6 is a block diagram of a general and/or special purpose computer600, which may be a general and/or special purpose computing device, inaccordance with some of the example embodiments of the invention. Thecomputer 600 may be, for example, the same or similar to client device(e.g., 504, FIG. 5), a user computer, a client computer and/or a servercomputer (e.g., 502, FIG. 5), among other things, or can be a device notoperative to communicate with a server.

The computer 600 may include without limitation a processor device 610,a main memory 625, and an interconnect bus 605. The processor device 610may include without limitation a single microprocessor, or may include aplurality of microprocessors for configuring the computer 600 as amulti-processor system. The main memory 625 stores, among other things,instructions and/or data for execution by the processor device 610. Themain memory 625 may include banks of dynamic random access memory(DRAM), as well as cache memory.

The computer 600 may further include a mass storage device 630,peripheral device(s) 640, portable non-transitory storage mediumdevice(s) 650, input control device(s) 680, a graphics subsystem 660,and/or an output display interface 670. For explanatory purposes, allcomponents in the computer 600 are shown in FIG. 6 as being coupled viathe bus 605. However, the computer 600 is not so limited. Devices of thecomputer 600 may be coupled via one or more data transport means. Forexample, the processor device 610 and/or the main memory 625 may becoupled via a local microprocessor bus. The mass storage device 630,peripheral device(s) 640, portable storage medium device(s) 650, and/orgraphics subsystem 660 may be coupled via one or more input/output (I/O)buses. The mass storage device 630 may be a nonvolatile storage devicefor storing data and/or instructions for use by the processor device610. The mass storage device 630 may be implemented, for example, with amagnetic disk drive or an optical disk drive. In a software embodiment,the mass storage device 630 is configured for loading contents of themass storage device 630 into the main memory 625.

The portable storage medium device 650 operates in conjunction with anonvolatile portable storage medium, such as, for example, a compactdisc read only memory (CD-ROM), to input and output data and code to andfrom the computer 600. In some embodiments, the software for storinginformation may be stored on a portable storage medium, and may beinputted into the computer 600 via the portable storage medium device650. The peripheral device(s) 640 may include any type of computersupport device, such as, for example, an input/output (I/O) interfaceconfigured to add additional functionality to the computer 600. Forexample, the peripheral device(s) 640 may include a network interfacecard for interfacing the computer 600 with a network 620.

The input control device(s) 680 provide a portion of the user interfacefor a user of the computer 600. The input control device(s) 680 mayinclude a keypad and/or a cursor control device. The keypad may beconfigured for inputting alphanumeric characters and/or other keyinformation. The cursor control device may include, for example, ahandheld controller or mouse, a trackball, a stylus, and/or cursordirection keys. In order to display textual and graphical information,the computer 600 may include the graphics subsystem 660 and the outputdisplay 670. The output display 670 may include a display such as a CSTN(Color Super Twisted Nematic), TFT (Thin Film Transistor), TFD (ThinFilm Diode), OLED (Organic Light-Emitting Diode), AMOLED display(Active-matrix organic light-emitting diode), and/or liquid crystaldisplay (LCD)-type displays. The displays can also be touchscreendisplays, such as capacitive and resistive-type touchscreen displays.

The graphics subsystem 660 receives textual and graphical information,and processes the information for output to the output display 670.

Each component of the computer 600 may represent a broad category of acomputer component of a general and/or special purpose computer.Components of the computer 600 are not limited to the specificimplementations provided here.

Software embodiments of the example embodiments presented herein may beprovided as a computer program product, or software, that may include anarticle of manufacture on a machine-accessible or machine-readablemedium having instructions. The instructions on the non-transitorymachine-accessible machine-readable or computer-readable medium may beused to program a computer system or other electronic device. Themachine or computer-readable medium may include, but is not limited to,floppy diskettes, optical disks, CD-ROMs, and magneto-optical disks orother types of media/machine-readable medium suitable for storing ortransmitting electronic instructions. The techniques described hereinare not limited to any particular software configuration. They may findapplicability in any computing or processing environment. The terms“computer-readable”, “machine-accessible medium” or “machine-readablemedium” used herein shall include any medium that is capable of storing,encoding, or transmitting a sequence of instructions for execution bythe machine and that causes the machine to perform any one of themethods described herein. Furthermore, it is common in the art to speakof software, in one form or another (e.g., program, procedure, process,application, module, unit, logic, and so on) as taking an action orcausing a result. Such expressions are merely a shorthand way of statingthat the execution of the software by a processing system causes theprocessor to perform an action to produce a result.

Portions of the example embodiments of the invention may be convenientlyimplemented by using a conventional general purpose computer, aspecialized digital computer and/or a microprocessor programmedaccording to the teachings of the present disclosure, as is apparent tothose skilled in the computer art. Appropriate software coding mayreadily be prepared by skilled programmers using the teachings of thepresent disclosure.

Some embodiments may also be implemented by the preparation ofapplication-specific integrated circuits, field-programmable gatearrays, or by interconnecting an appropriate network of conventionalcomponent circuits.

Some embodiments include a computer program product. The computerprogram product may be a storage medium or media having instructionsstored thereon or therein which can be used to control, or cause, acomputer to perform any of the procedures of the example embodiments ofthe invention. The storage medium may include without limitation afloppy disk, a mini disk, an optical disc, a Blu-ray Disc, a DVD, a CDor CD-ROM, a micro-drive, a magneto-optical disk, a ROM, a RAM, anEPROM, an EEPROM, a DRAM, a VRAM, a flash memory, a flash card, amagnetic card, an optical card, nanosystems, a molecular memoryintegrated circuit, a RAID, remote data storage/archive/warehousing,and/or any other type of device suitable for storing instructions and/ordata.

Stored on any one of the computer-readable medium or media, someimplementations include software for controlling both the hardware ofthe general and/or special computer or microprocessor, and for enablingthe computer or microprocessor to interact with a human user or othermechanism utilizing the results of the example embodiments of theinvention. Such software may include without limitation device drivers,operating systems, and user applications. Ultimately, such computerreadable media further include software for performing example aspectsof the invention, as described above.

Included in the programming and/or software of the general and/orspecial purpose computer or microprocessor are software modules forimplementing the procedures described above.

While various example embodiments of the present invention have beendescribed above, it should be understood that they have been presentedby way of example, and not limitation. It will be apparent to personsskilled in the relevant art(s) that various changes in form and detailcan be made therein. Thus, the present invention should not be limitedby any of the above described example embodiments, but should be definedonly in accordance with the following claims and their equivalents.

In addition, it should be understood that the FIGS. 1-6 are presentedfor example purposes only. The architecture of the example embodimentspresented herein is sufficiently flexible and configurable, such that itmay be utilized and navigated in ways other than that shown in theaccompanying figures.

Further, the purpose of the foregoing Abstract is to enable the U.S.Patent and Trademark Office and the public generally, and especially thescientists, engineers and practitioners in the art who are not familiarwith patent or legal terms or phraseology, to determine quickly from acursory inspection the nature and essence of the technical disclosure ofthe application. The Abstract is not intended to be limiting as to thescope of the example embodiments presented herein in any way. It is alsoto be understood that the procedures recited in the claims need not beperformed in the order presented.

1.-21. (canceled)
 22. A method for providing an interface for managingaffinity-related information, comprising the steps of: collecting, by acollection unit: user interaction data associated with a user accountand corresponding to a plurality of content creators, social media dataassociated with the user account, and attribute data describingattributes of the plurality of content creators; computing, based on theuser interaction data, the social media data, and the attribute data, anaffinity score that quantifies the affinity of the user account to aparticular content creator of the plurality of content creators; storingthe affinity score on a data store communicatively coupled to a network;and providing to a dashboard system on the network access to theaffinity score associated with the particular content creator.
 23. Themethod according to claim 22 further including a step of generating aranking of the stored affinity score against a plurality of affinityscores of one or more other user accounts corresponding to the contentcreator.
 24. The method according to claim 23 further including a stepof categorizing the user account into one or more groups using theaffinity score or the ranking generated for the affinity score.
 25. Themethod according to claim 24, wherein one of the one or more groupsincludes only user accounts having affinity scores that increased atleast a threshold amount over a time period.
 26. The method according toclaim 24 further including a step of periodically updating the affinityscore using a most recent activity data of the user accountcorresponding to the content creator.
 27. A device configured to manageaffinity-related information, the device comprising: a collection unitconfigured to collect: user interaction data associated with a useraccount and corresponding to a plurality of content creators, socialmedia data associated with the user account, and attribute datadescribing attributes of the plurality of content creators; a scoregeneration unit configured to generate, based on the user interactiondata, the social media data, and the attribute data, an affinity scorethat quantifies the affinity of the user account to a particular contentcreator of the plurality of content creators; and a data store,configured to store the affinity score on a data store communicativelycoupled to a network and provide to a dashboard system on the networkaccess to the affinity score associated with the particular contentcreator.
 28. The device according to claim 27 further including aranking unit configured to rank the affinity score against affinityscores of one or more other user accounts corresponding to the contentcreator.
 29. The device according to claim 28 further including acategorization unit configured to categorize the user account into oneor more groups using the ranking of the affinity score produced by theranking unit.
 30. The device according to claim 29, wherein one of theone or more groups includes only user accounts having affinity scoresthat increased at least a threshold amount over a time period.
 31. Thedevice according to claim 27, wherein the computing unit is furtherconfigured to update the affinity score periodically using a most recentactivity data of the user account corresponding to the content creator.32. The device according to claim 27, wherein the collection unit isconfigured to collect at least a portion of the total activity data forthe user account from at least one data source external to the contenthosting platform.
 33. A non-transitory computer-readable medium havinginstructions stored therein that in response to execution by a devicecause the device to perform operations comprising: computing affinityscores for a plurality of user accounts, each affinity score quantifyingaffinity of a user account to one of a plurality of content creators ofone or more digital objects hosted in a content hosting platform,wherein computing an affinity score includes: collecting interactiondata for the user account corresponding to a content creator;normalizing the collected interaction data using a total activity dataof the user account on the content hosting platform and attribute dataassociated with the content creator, and generating the affinity scoreusing the normalized interaction data.
 34. The non-transitorycomputer-readable medium of claim 33, wherein the operations furtherinclude a step of ranking the affinity score against affinity scores ofone or more other user accounts corresponding to the content creator.35. The non-transitory computer-readable medium of claim 34, wherein theoperations further include a step of categorizing the user account intoone or more groups using the step of ranking the affinity score amongaffinity scores of one or more other user accounts corresponding to thecontent creator.
 36. The non-transitory computer-readable medium ofclaim 35, wherein one of the one or more groups includes only useraccounts having affinity scores that increased at least a thresholdamount over a time period.
 37. The non-transitory computer-readablemedium of claim 33, wherein the operations further include a step ofperiodically updating the affinity score using a most recent activitydata of the user account corresponding to the content creator.
 38. Thenon-transitory computer-readable medium of claim 33, wherein at least aportion of the total activity data for the user account is collectedfrom at least one data source external to the content hosting platform.